Open Bug 1803590 Opened 3 years ago Updated 2 years ago

Define the categories in a YAML or JSON file outside of perf.py

Categories

(Testing :: Performance, task, P2)

Product:
Testing
Component:
Performance
Type:
task

Tracking

(Not tracked)

Status:
ASSIGNED

People

(Reporter: sparky, Assigned: aglavic)

References

(Blocks 1 open bug)

Details

(Whiteboard: fxp)

Attachments

(1 obsolete file)

Currently we define our categories within the perf.py selector file. We should move it outside to a YAML or JSON file.

Assignee: nobody → aglavic
Whiteboard: fxp

Hey Sparky, I wanted to get your thoughts on where you want the categories defined?
I was personally thinking in to probably put it in mozilla-unified/tools/performance or maybe somethere in mozilla-unified/tools/tryselect/util, mozilla-unified/tools/tryselect/selectors/chooser/static, or mozilla-unified/tools/tryselect/selectors/chooser/templates

Flags: needinfo?(gmierz2)

Maybe we could use testing/performance/mach-try-perf? With testing/performance, that will trigger the herald rule and add us as reviewers for those changes. I'm not sure if we can access that file in our CI tests, but we could provide a test file similar to how we've defined test categories.

Flags: needinfo?(gmierz2)
Attachment #9328688 - Attachment description: WIP: Bug 1803590 - Define performance categories outside of perf.py r?#perftest → Bug 1803590 - Define performance categories outside of perf.py r?#perftest
Attachment #9328688 - Attachment is obsolete: true

Was blocked on waiting for perf.py refactoring, will be taking a look now

Flags: needinfo?(aglavic)
Status: NEW → ASSIGNED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: